home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000334_news@columbia.edu _Mon Mar 3 11:14:14 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA04411
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 3 Mar 1997 11:14:14 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA27288
for kermit.misc@watsun; Mon, 3 Mar 1997 11:14:13 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: FAST+FAST->Window slots 1 of 20
Date: 3 Mar 1997 16:14:12 GMT
Organization: Columbia University
Lines: 32
Message-ID: <5fetck$bde$1@apakabar.cc.columbia.edu>
References: <5fb64g$5fp@nntp.Stanford.EDU>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6673
In article <5fb64g$5fp@nntp.Stanford.EDU>,
Stewart Levin <stew@taal.Stanford.EDU> wrote:
: C-Kermit 6.0.192 on both ends (Linux and Sun OS 4.1.3)
: Binary file transfer mode
: FAST invoked on both ends before transfer
:
: SEND'ing a large file from the Sun to the PC produces
: 20 rapid packets followed by a much slower one-at-a-time
: crawl and the message that I am using 1 of 20 window slots.
: Cancelling the file takes 20 more packets to complete.
:
This means the round-trip delay is significantly longer than
the time it takes to transmit 20 packets. Sind the FAST macro
gives you a packet length of 4K, that means 80K worth of packets.
What happens if you increase the window slots to 30 (which
is close to the maximum)? If the connection is clean
(no retransmissions) then you can also try increasing the packet
length up to 8 or 9K.
On the other hand, if the delays are not due to connection
latency, none of this will help -- there is another bottleneck
that you need to indentify, most likely limited capacity of the
receiving computer or other intermediate device (such as a
terminal server). In that case, there's not much you can do in
Kermit to overcome the limitations of the underlying connection;
you'll need to address them directly.
But first see if you can narrow down exactly where the bottleneck
is.
- Frank